Multi-site disaster recovery consistency group for heterogeneous systems

ABSTRACT

Methods and arrangements for managing a consistency group for computing sites. A plurality of computing sites are communicated with, each of the sites comprising one or more of (i) and (ii): (i) at least one virtual machine; and (ii) at least one server. Updates captured at each of the sites are received, and the captured updates are batched. The batched updates are communicated to the plurality of sites, thereby ensuring data consistency across the plurality of sites. Other variants and embodiments are broadly contemplated herein.

BACKGROUND

As is generally known, a consistency group (CG) serves to group allsystem, middleware, and application volumes that are to be managed as aconsistent entity. Among other settings, this can be of relevance in ahybrid cloud, which itself involves consolidation and management of apublic cloud, private cloud and dedicated hardware. As is generallyknown, hypervisors can serve in the provision of consistency groups forVMs (virtual machines). It is also known that storage controllers canserve in the provision of block-level consistency groups.

However, several problems and shortcomings have been notedconventionally. Physical boundaries are encountered because hypervisorsnormally provide CGs solely for VMs within a privately managedvirtualized environment, while the scope of a storage controller's CG isnormally limited to hosts having attached storage (e.g., logical unitnumbers or LUNs) provisioned by one or more controllers. Logicalboundaries are usually encountered because CGs are conventionallyfacilitated only within a data center, a public cloud or a privatecloud. Further, homogeneity emerges as a problem because it is difficultto provide CGs for applications spanning across VMs and physicalmachines.

BRIEF SUMMARY

In summary, one aspect of the invention provides a method of managing aconsistency group, the method comprising: utilizing at least oneprocessor to execute computer code configured to perform the steps of:communicating with a plurality of computing sites, each of the sitescomprising one or more of (i) and (ii): (i) at least one virtualmachine; and (ii) at least one server; receiving updates captured ateach of the sites; batching the captured updates; and communicating thebatched updates to the plurality of sites, thereby ensuring dataconsistency across the plurality of sites.

Another aspect of the invention provides an apparatus for managing aconsistency group for computing sites, the apparatus comprising: atleast one processor; and a computer readable storage medium havingcomputer readable program code embodied therewith and executable by theat least one processor, the computer readable program code comprising:computer readable program code configured to communicate with aplurality of computing sites, each of the sites comprising one or moreof (i) and (ii): (i) at least one virtual machine; and (ii) at least oneserver; computer readable program code configured to receive updatescaptured at each of the sites; computer readable program code configuredto batch the captured updates; and computer readable program codeconfigured to communicate the batched updates to the plurality of sites,thereby ensuring data consistency across the plurality of sites.

An additional aspect of the invention provides a computer programproduct for managing a consistency group for computing sites, thecomputer program product comprising: a computer readable storage mediumhaving computer readable program code embodied therewith, the computerreadable program code comprising: computer readable program codeconfigured to communicate with a plurality of computing sites, each ofthe sites comprising one or more of (i) and (ii): (i) at least onevirtual machine; and (ii) at least one server; computer readable programcode configured to receive updates captured at each of the sites;computer readable program code configured to batch the captured updates;and computer readable program code configured to communicate the batchedupdates to the plurality of sites, thereby ensuring data consistencyacross the plurality of sites.

A further aspect of the invention provides a method comprising:providing an aggregator in communication with a plurality of sitescollectively forming a consistency group, each of the sites comprisingone or more of (i) and (ii): (i) at least one virtual machine; and (ii)at least one server; receiving, at the aggregator, updates which arecaptured at each of the sites periodically, the captured updatescomprising file system snapshots; batching the captured updates at theaggregator; and communicating the batched updates from the aggregator tothe plurality of sites, thereby ensuring data consistency across theplurality of sites.

For a better understanding of exemplary embodiments of the invention,together with other and further features and advantages thereof,reference is made to the following description, taken in conjunctionwith the accompanying drawings, and the scope of the claimed embodimentsof the invention will be pointed out in the appended claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates conventional arrangements for providing consistencygroups for virtual machines and with respect to storage controllers.

FIG. 2 schematically illustrates a conventional disaster recovery (DR)arrangement.

FIG. 3 schematically illustrates a hybrid consistency group inaccordance with at least one embodiment of the invention.

FIG. 4 schematically illustrates a variant embodiment of a hybridconsistency group in accordance with at least one embodiment of theinvention.

FIG. 5 sets forth a process more generally for managing a consistencygroup for computing sites.

FIG. 6 illustrates a computer system.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments ofthe invention, as generally described and illustrated in the figuresherein, may be arranged and designed in a wide variety of differentconfigurations in addition to the described exemplary embodiments. Thus,the following more detailed description of the embodiments of theinvention, as represented in the figures, is not intended to limit thescope of the embodiments of the invention, as claimed, but is merelyrepresentative of exemplary embodiments of the invention.

Reference throughout this specification to “one embodiment” or “anembodiment” (or the like) means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the invention. Thus, appearances of thephrases “in one embodiment” or “in an embodiment” or the like in variousplaces throughout this specification are not necessarily all referringto the same embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in at least one embodiment. In thefollowing description, numerous specific details are provided to give athorough understanding of embodiments of the invention. One skilled inthe relevant art may well recognize, however, that embodiments of theinvention can be practiced without at least one of the specific detailsthereof, or can be practiced with other methods, components, materials,et cetera. In other instances, well-known structures, materials, oroperations are not shown or described in detail to avoid obscuringaspects of the invention.

The description now turns to the figures. The illustrated embodiments ofthe invention will be best understood by reference to the figures. Thefollowing description is intended only by way of example and simplyillustrates certain selected exemplary embodiments of the invention asclaimed herein.

Specific reference will now be made here below to FIG. 1-4. It should beappreciated that the processes, arrangements and products broadlyillustrated therein can be carried out on, or in accordance with,essentially any suitable computer system or set of computer systems,which may, by way of an illustrative and non-restrictive example,include a system or server such as that indicated at 12′ in FIG. 6. Inaccordance with an exemplary embodiment, most if not all of the processsteps, components and outputs discussed with respect to FIGS. 1-4 can beperformed or utilized by way of a processing unit or units and systemmemory such as those indicated, respectively, at 16′ and 28′ in FIG. 6,whether on a server computer, a client computer, a node computer in adistributed network, or any combination thereof.

Broadly contemplated herein, in accordance with at least one embodimentof the invention, are methods and arrangements which provide systemsheterogeneity at a primary site. Such heterogeneity can be manifested interms of any and all of: operating systems, storage type (e.g., DAS,SAN, NAS), physical location (e.g., storage could be provisioned fromdifferent controllers at different sites), and server type (e.g., VM orPhysical Server). (In the ensuing discussion, “server” may be understoodto indicate a physical server as generally known in the computing arts.)Additionally, there are broadly contemplated herein methods andarrangements wherein a consistent state, comprising current states for aset of VMs or servers, are captured periodically and incrementally, andbatched together at an aggregator. In this connection, and as broadlyunderstood herein, this capturing involves capturing of current stateswith respect to each VM or server, and the captured states may bereferred to as “updates” or “system updates”. As such, during recovery,these batched updates can be applied to the set of VMs or servers torestore a consistent state relative to each other. Furthermore, it willbe appreciated that there are broadly contemplated herein systems andarrangements which provide consistency groups across VMs and servers incross-site/hybrid cloud environments using global coordination and localconsistency. Additionally, methods and arrangements as broadlycontemplated herein provide a CG for VMs or servers provisioned with adisk space from different storage types (e.g., DAS, NAS, SAN, vDisk). Inaccordance with various features broadly contemplated herein, localconsistency can be ensured through incremental file system snapshots,and heterogeneity can be facilitated among members of a CG. These andother features relating to at least one embodiment of the invention willbe better appreciated from the discussion which follows.

As generally understood herein, in accordance with at least oneembodiment of the invention, a consistency group (CG) represents agrouping of all system, middleware and application volumes for which itis desired or required to be managed as a consistent entity. Among otherbenefits, CGs ensure that data are maintained in one form or anotheracross the entire group, since considerations for such maintenance aredifferent than in the case of data consistency at merely a database,file system or application level. Such benefits can be of advantage insettings such as disaster recovery, where data may remain consistentacross one or more locations or volumes serving in a role of databackup.

FIG. 1 illustrates conventional arrangements for providing consistencygroups for virtual machines and with respect to storage controllers. Asshown, in a first cloud setting 101, a CG 103 is defined with respect toseveral VMs run by a hypervisor 105, and in a second cloud setting 107 aCG 109 is defined with respect to hosts and LUNs provisioned or mediatedby a storage controller 111. In both settings, design constraintsinhibit further definition of CGs that might otherwise help impartgreater utility. Generally, in cloud setups such as those indicated at101 and 105, hardware (e.g., a hypervisor 109 or storage controller 111)is abstracted, so there is little or no control or access to thehardware. Inasmuch as a hybrid cloud requirement can involvehardware-agnosticity, even a cross-site CG requiring hardware access maywell not work. Further, it is recognized that some solutions could beprovided by embedding a snapshot feature in data paths. However, thismay involve patching or updating a guest or host OS kernel, which can bedifficult in a cloud setting; e.g., owing to standardization, cloudimages can often be very restrictive and thus difficult to “intrude”.

FIG. 2 schematically illustrates a conventional disaster recovery (DR)arrangement, by way of conveying additional challenges that may often beencountered. Such an arrangement can support DR wherein multiple primarysites can be mapped to a single secondary site. As shown, there arethree sites 213 a/b/c each including a SAN (storage area network) andSAN volume controller (SVC); storage volumes in the SAN are depicted bycylindrical shapes. (By way of a non-restrictive and illustrativeexample, International Business Machines of Armonk, N.Y., has developeda SVC that can be used as a block storage virtualization appliance.)Also shown is a DR site 215 including an SVC and SAN. Here, variousvolumes can be mirrored or duplicated at a DR site; e.g., V1 from site213 a, V2 from site 213 b and V3 from site 213 c. However, the inclusionof V1, V2 and V3 at site 215 does not correlate to being part of thesame consistency group.

FIG. 3 schematically illustrates a hybrid consistency group inaccordance with at least one embodiment of the invention, while FIG. 4schematically illustrates a variant embodiment of a hybrid consistencygroup. Reference may continue to be made to both figures throughout theensuing discussion.

In accordance with at least one embodiment of the invention, in theexample of FIG. 3, an aggregation site 317 for defining a hybrid CG isprovided, and includes an aggregator and backup storage. By way ofillustrative example, a plurality of sites 321 a/b/c/d/e may eachinclude various storage volumes or spaces that may each form aconstituent part of the same CG. Thus, site 321 a includes a controllerC1′ and volume V1′, site 321 b includes a controller C2′ and volume V2′.On the other hand, in the present example, site 321 c includes a virtualdisk (vDisk), site 321 d includes a high density disk (HDD), and site321 e includes network attached storage (NAS). A layer 319 is defined byvirtual machines and servers that are each in communication with therespective sites as shown (wherein Server2′ in particular communicatesvia a WAN [wide area network] with site 321 e), and each of the VMs andservers is in communication with an agent which serves to capture systemsnapshots with respect to each site 321 a/b/c/d/e.

In accordance with at least one embodiment of the invention, the exampleof FIG. 4 shows a different setting involving a public cloud 423,private cloud 425 and set of dedicated servers 427; each of these formpart of a hybrid consistency group (HyCG) 429. Communication via a WANaffords a connection with a secondary storage site 431.

In accordance with at least one embodiment of the invention, consistentwith the examples shown in FIGS. 3 and 4, it can be appreciated that aCG is built using two primitives, “local consistency” and “globalco-ordination”. For “local consistency”, an agent at each site takesfile system snapshots and replicates incremental snapshots. For “globalco-ordination”, agents running on VMs (or servers) participating in a CGwill co-ordinate timing for taking snapshots; such coordination may bemanaged by the aggregator acting as a central communication hub.Deduplication can also be ensured via snapshot backup in any suitableform.

As such, in accordance with at least one embodiment of the invention,incremental file system snapshots are taken by an agent (e.g., at 319)running at each site (e.g., 321 a/b/c/d/e) forming part of a CG. Changeswith respect to a local file system can thereby be monitored, and changelogs can also be stored upon every snapshot being taken. Thus, thechange logs and the file system changes serve to maintain localconsistency. Each individual agent will then process the change logs anddata from its snapshot directory, and will notify an aggregator (e.g.,at 317) once it finishes processing all the changes for a particularsnapshot.

In accordance with at least one embodiment of the invention, incrementalsnapshots can also be made at an aggregator (e.g., at 317), with respectto the system snapshots batched there from the various sites. Further,if multiple aggregators are provided, consistency can be achieved in thesame manner as discussed above with respect to individual agents and anaggregator; in other words, multiple aggregators may themselves feeddata to another aggregator at a higher level of organizationalhierarchy.

In accordance with at least one embodiment of the invention, anaggregator (e.g., at 317) receives, batches and deduplicates datachanges with respect to all VMs and/or servers. Once it receives amarker (e.g., “END SNAPSHOT”) from all the VMs and/or servers in the CG,it will take a snapshot of its own repository. Incremental backup (e.g.,to the backup at site 317 in FIG. 3 or to secondary site 431 in FIG. 4)can be performed via recursive or relayed replication. Communication ofthe batched/deduplicated data changes from the aggregator (e.g., at 317)to all of the sites in the CG (e.g., at 321 a/b/c/d/e) may then takeplace, thereby ensuring data consistency across all sites in the CG.While this can be performed under any suitable conditions, the valuethereof may be appreciated in particular when restoring a consistentstate throughout all sites in the CG in response to one or moredisruptive events (i.e., one or more events that disrupt data at one ormore of the sites), e.g., as a component of disaster recovery.

In accordance with at least one embodiment of the invention,quantitative scores and values as determined herein can be stored inmemory or displayed to a user on a screen, as might fit the needs of oneor more users.

FIG. 5 sets forth a process more generally for managing a consistencygroup for computing sites, in accordance with at least one embodiment ofthe invention. It should be appreciated that a process such as thatbroadly illustrated in FIG. 5 can be carried out on essentially anysuitable computer system or set of computer systems, which may, by wayof an illustrative and non-restrictive example, include a system such asthat indicated at 12′ in FIG. 6. In accordance with an exampleembodiment, most if not all of the process steps discussed with respectto FIG. 5 can be performed by way of a processing unit or units andsystem memory such as those indicated, respectively, at 16′ and 28′ inFIG. 6.

As shown in FIG. 5, in accordance with at least one embodiment of theinvention, a plurality of computing sites are communicated with, each ofthe sites comprising one or more of (i) and (ii): (i) at least onevirtual machine; and (ii) at least one server (502). Updates captured ateach of the sites are received (504), and the captured updates arebatched (506). The batched updates are communicated to the plurality ofsites, thereby ensuring data consistency across the plurality of sites(508).

Referring now to FIG. 6, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10′ is only one example of asuitable cloud computing node and is not intended to suggest anylimitation as to the scope of use or functionality of embodiments of theinvention described herein. Regardless, cloud computing node 10′ iscapable of being implemented and/or performing any of the functionalityset forth hereinabove. In accordance with embodiments of the invention,computing node 10′ may not necessarily even be part of a cloud networkbut instead could be part of another type of distributed or othernetwork, or could represent a stand-alone node. For the purposes ofdiscussion and illustration, however, node 10′ is variously referred toherein as a “cloud computing node”.

In cloud computing node 10′ there is a computer system/server 12′, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12′ include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12′ may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12′ may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 6, computer system/server 12′ in cloud computing node10 is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12′ may include, but are notlimited to, at least one processor or processing unit 16′, a systemmemory 28′, and a bus 18′ that couples various system componentsincluding system memory 28′ to processor 16′. Bus 18′ represents atleast one of any of several types of bus structures, including a memorybus or memory controller, a peripheral bus, an accelerated graphicsport, and a processor or local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnects (PCI) bus.

Computer system/server 12′ typically includes a variety of computersystem readable media. Such media may be any available media that areaccessible by computer system/server 12′, and include both volatile andnon-volatile media, removable and non-removable media.

System memory 28′ can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30′ and/or cachememory 32′. Computer system/server 12′ may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34′ can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18′ by at least one datamedia interface. As will be further depicted and described below, memory28′ may include at least one program product having a set (e.g., atleast one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40′, having a set (at least one) of program modules 42′,may be stored in memory 28′ (by way of example, and not limitation), aswell as an operating system, at least one application program, otherprogram modules, and program data. Each of the operating systems, atleast one application program, other program modules, and program dataor some combination thereof, may include an implementation of anetworking environment. Program modules 42′ generally carry out thefunctions and/or methodologies of embodiments of the invention asdescribed herein.

Computer system/server 12′ may also communicate with at least oneexternal device 14′ such as a keyboard, a pointing device, a display24′, etc.; at least one device that enables a user to interact withcomputer system/server 12; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 12′ to communicate withat least one other computing device. Such communication can occur viaI/O interfaces 22′. Still yet, computer system/server 12′ cancommunicate with at least one network such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20′. As depicted, network adapter 20′communicates with the other components of computer system/server 12′ viabus 18′. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12′. Examples include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

This disclosure has been presented for purposes of illustration anddescription but is not intended to be exhaustive or limiting. Manymodifications and variations will be apparent to those of ordinary skillin the art. The embodiments were chosen and described in order toexplain principles and practical application, and to enable others ofordinary skill in the art to understand the disclosure.

Although illustrative embodiments of the invention have been describedherein with reference to the accompanying drawings, it is to beunderstood that the embodiments of the invention are not limited tothose precise embodiments, and that various other changes andmodifications may be affected therein by one skilled in the art withoutdeparting from the scope or spirit of the disclosure.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited took, an electronic storage device, a magnetic storagedevice, an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions. These computer readable programinstructions may be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing thefunctions/acts specified in the flowchart and/or block diagram block orblocks. These computer readable program instructions may also be storedin a computer readable storage medium that can direct a computer, aprogrammable data processing apparatus, and/or other devices to functionin a particular manner, such that the computer readable storage mediumhaving instructions stored therein comprises an article of manufactureincluding instructions which implement aspects of the function/actspecified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A method of managing a consistency group forcomputing sites, said method comprising: utilizing at least oneprocessor to execute computer code configured to perform the steps of:communicating, using an aggregator, with a plurality of computing sitescontained within a consistency group, wherein each of the plurality ofcomputing sites comprises one or more of (i) and (ii): (i) at least onevirtual machine; and (ii) at least one server; receiving, using theaggregator, updates captured at each of the plurality of computingsites; comparing, using the aggregator, the received updates from atleast one of the plurality of computing sites to data, wherein the datacomprises the received updates from another of the plurality ofcomputing sites and a repository of the aggregator; deduplicating, usingthe aggregator, the received updates based upon the comparing; batching,using the aggregator, the deduplicated updates; and communicating, usingthe aggregator, the batched updates to the plurality of computing sites.2. The method according to claim 1, wherein the captured updatescomprise updates captured periodically.
 3. The method according to claim2, wherein the captured updates comprise updates captured periodicallyand incrementally.
 4. The method according to claim 1, wherein thecaptured updates comprise file system snapshots.
 5. The method accordingto claim 4, wherein the file system snapshots comprise snapshots takenperiodically.
 6. The method according to claim 5, wherein the filesystem snapshots comprise snapshots taken periodically andincrementally.
 7. The method according to claim 4, comprisingcoordinating timing of the file system snapshots across the plurality ofcomputing sites.
 8. The method according to claim 1, wherein thecaptured updates are received from a plurality of agents associated withthe plurality of computing sites.
 9. The method according to claim 1,wherein said communicating the batched updates to the plurality ofcomputing sites is performed in restoring a consistent state in responseto one or more disruptive events.
 10. The method according to claim 9,wherein said restoring is performed as a component of disaster recovery.11. The method according to claim 1, comprising storing the batchedupdates in a backup storage in communication with the aggregator. 12.The method according to claim 1, comprising taking a system snapshot atthe aggregator upon said batching of the deduplicated updates.
 13. Anapparatus for managing a consistency group for computing sites, saidapparatus comprising: at least one processor; and a computer readablestorage medium having computer readable program code embodied therewithand executable by the at least one processor, the computer readableprogram code comprising: computer readable program code configured tocommunicate, using an aggregator, with a plurality of computing sitescontained within a consistency group, wherein each of the plurality ofcomputing sites comprises one or more of (i) and (ii): (i) at least onevirtual machine; and (ii) at least one server; computer readable programcode configured to receive, using the aggregator, updates captured ateach of the plurality of computing sites; computer readable program codeconfigured to compare, using the aggregator, the received updates fromat least one of the plurality of computing sites to data, wherein thedata comprises the received updates from another of the plurality ofcomputing sites and a repository of the aggregator; computer readableprogram code configured to deduplicate, using the aggregator, thereceived updates based upon the comparing; computer readable programcode configured to batch, using the aggregator, the deduplicatedupdates; and computer readable program code configured to communicate,using the aggregator, the batched updates to the plurality of computingsites.
 14. A computer program product for managing a consistency groupfor computing sites, said computer program product comprising: acomputer readable storage medium having computer readable program codeembodied therewith, the computer readable program code comprising:computer readable program code configured to communicate, using anaggregator, with a plurality of computing sites contained within aconsistency group, wherein each of the plurality of computing sitescomprises one or more of (i) and (ii): (i) at least one virtual machine;and (ii) at least one server; computer readable program code configuredto receive, using the aggregator, updates captured at each of theplurality of computing sites; computer readable program code configuredto compare, using the aggregator, the received updates from at least oneof the plurality of computing sites to data, wherein the data comprisesthe received updates from another of the plurality of computing sitesand a repository of the aggregator; computer readable program codeconfigured to deduplicate, using the aggregator, the received updatesbased upon the comparing; computer readable program code configured tobatch, using the aggregator, the deduplicated updates; and computerreadable program code configured to communicate, using the aggregator,the batched updates to the plurality of computing sites.
 15. Thecomputer program product according to claim 14, wherein the capturedupdates comprise updates captured periodically.
 16. The computer programproduct according to claim 14, wherein the captured updates comprisefile system snapshots.
 17. A method comprising: providing at least oneaggregator in communication with a plurality of computing sitescollectively forming a consistency group, wherein each of the pluralityof computing sites comprises one or more of (i) and (ii): (i) at leastone virtual machine; and (ii) at least one server; receiving, using theat least one aggregator, updates which are captured at each of theplurality of computing sites periodically, wherein the captured updatescomprise file system snapshots; comparing, using the at least oneaggregator, the received updates from at least one of the plurality ofcomputing sites to data, wherein the data comprises the received updatesfrom another of the plurality of computing sites and a repository of theaggregator; deduplicating, using the at least one aggregator, thereceived updates based upon the comparing; batching, using the at leastone aggregator, the deduplicated updates and communicating, using the atleast one aggregator, the batched updates to the plurality of computingsites.